Received: from relay3.UU.NET (relay3.UU.NET [192.48.96.8]) by keeper.albany.net (8.7.1/8.7.1) with ESMTP id XAA29248 for <dwarner@albany.net>; Mon, 18 Dec 1995 23:48:41 -0500 (EST)
Received: from garcia.com by relay3.UU.NET with SMTP
id QQzusx29020; Mon, 18 Dec 1995 23:47:48 -0500 (EST)
Received: from (localhost) by garcia.com (5.x/SMI-SVR4)
id AA03417; Mon, 18 Dec 1995 23:48:04 -0500
Date: Mon, 18 Dec 1995 23:48:04 -0500
Errors-To: dwarner@albany.net
Message-Id: <30D56C0F.5824@cats.ucsc.edu>
Errors-To: dwarner@albany.net
Reply-To: lightwave@garcia.com
Originator: lightwave@garcia.com
Sender: lightwave@garcia.com
Precedence: bulk
From: Adam Chrystie <adamchry@cats.ucsc.edu>
To: Multiple recipients of list <lightwave@garcia.com>
Subject: Re: LW Frame limits?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO
X-Status:
Ernie Wright wrote:
> That's pretty funny, and I think I know what's happening. 24,464 is
> what you get when you only look at the lower two bytes of 90,000. Or:
>
> 90000 = 01 5F 90h
> 24464 = 00 5F 90h
>
> The loss of the bits above the 15th could have been an effect of using
> certain Windows functions to handle the frame number fields on the
> Scene panel, but a quick check on the Amiga also shows this behavior,
> which implies that LW itself is using a 16-bit integer to store frame
> numbers.
GREAT!! haha...I'm just learning about this in our Intro to C book..
>
> The actual limit, in effect, is 32,767. And if David had needed, say,
> 100,000 frames instead of 90,000, the Last Frame value displayed on the